-
Notifications
You must be signed in to change notification settings - Fork 805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add supported CPython/PyPy versions to cargo package metadata #4756
base: main
Are you sure you want to change the base?
Add supported CPython/PyPy versions to cargo package metadata #4756
Conversation
7a38b06
to
1aaca98
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, do you think there's a way that we can test this? Maybe a small nox
job which inspects the output of cargo metadata
?
1aaca98
to
a2d6030
Compare
Test added. |
a2d6030
to
0bc5125
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, the structure of this looks good to me. Sorry this got stuck in review limbo for so long.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder, can we generate PY_VERSIONS
and PYPY_VERSIONS
in this file from the metadata?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds doable.
@@ -44,6 +44,8 @@ def test(session: nox.Session) -> None: | |||
|
|||
@nox.session(name="test-rust", venv_backend="none") | |||
def test_rust(session: nox.Session): | |||
_run_cargo_package_metadata_test(session, packages=["pyo3", "pyo3-ffi"]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will pyo3
and pyo3-ffi
always support exactly the same versions? I guess so. Should we ensure their metadata is always in sync? Or should we have it only on pyo3-ffi
? 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or should we have it only on
pyo3-ffi
?
Good point, I think have it only on a leaf dependency makes sense!
Co-authored-by: David Hewitt <[email protected]>
I tried to use workspace inheritance to reduce duplication, but when inspecting the
cargo package
artifact It does not seem to work.Closes #4751